Skip to content

Conversation

@cgillum
Copy link
Member

@cgillum cgillum commented Mar 31, 2025

We're missing some basic execution logs in this SDK. For Azure Functions, this was okay because the Functions host and worker layer would sufficiently take care of logging. However, for standalone use, the base logging was insufficient.

This PR adds basic execution starting, completion, and failure logs for orchestrations and activities.

@cgillum cgillum requested review from halspang, jviau and nytian March 31, 2025 22:44
philliphoff
philliphoff previously approved these changes Mar 31, 2025
jviau
jviau previously approved these changes Apr 1, 2025
Copy link
Member

@jviau jviau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good to have more logging. Do we have plans for distributed tracing in this library directly? These specific logs are more valuable as spans, as that will capture all of the same information but in a more usable way.

No harm in having these logs as well though - but I suggest putting the log level to Debug as if spans are ever added, these would be lower importance.

jviau
jviau previously approved these changes Apr 2, 2025
@cgillum cgillum merged commit 745bf47 into main Apr 2, 2025
4 checks passed
@cgillum cgillum deleted the cgillum/log-improvements branch April 2, 2025 21:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants